QENEX Pulse Scanner

If you see HTTP or DNS traffic in your access logs originating from the User-Agent below, an enterprise customer using QENEX Pulse (continuous third-party risk monitoring, pulse.qenex.ai) has added your domain to their monitored vendor portfolio.

User-Agent

Mozilla/5.0 (compatible; QenexPulseScanner/1.0; +https://qenex.ai/scanner; tech-ops@qenex.ai)

Source IP

198.244.164.221

Rate limit (per target)

≤ 12 requests / minute

Default scan cadence

Once per 24 h, per vendor

What we check

Only public-facing technical configuration. No authentication probes, no port scanning beyond standard service ports, no application-layer fuzzing.

Email security: SPF, DKIM, DMARC, MTA-STS
Transport security: TLS certificate chain & expiry
DNS integrity: DNSSEC delegation status
Subdomain takeover: CNAMEs pointing at unclaimed third-party services, with body-fingerprint + 4xx-status second-stage confirmation to avoid false positives
WHOIS / RDAP: registration status & expiry
Authoritative published security contacts: /.well-known/security.txt (RFC 9116) + RDAP abuse entries

Why this benefits you

Every probe result is hashed, pinned to IPFS, and timestamped to the Bitcoin blockchain via OpenTimestamps. If you ever need to dispute a finding, you can verify the exact data we observed at the exact moment we observed it — without trusting QENEX's word.

If you want us to throttle, exclude your domain, or coordinate a scan window

Email security@qenex.ai with the domain and the timing window you'd like. Standard turnaround: same business day.