Skip to content

Hostname

wpgateways.com

Last fetched

wpgateways.com resolves to 104.21.28.55, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. wpgateways.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · wpgateways.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/wpgateways.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
mohsin zunzunia
Contact emails
mohsinoffline@gmail.com, 4bd358c976fc4863a9ef5cbbf2f71148.protect@whoisguard.com, 5d7c36251a1845f0976d97b5feb1741e.protect@withheldforprivacy.com, 78b824fa5b07428c8c3ea9c288b667d0.protect@withheldforprivacy.com

Subdomains

Subdomain
7a870b97a507.wpgateways.com
autodiscover.wpgateways.com
cpanel.wpgateways.com
cpcalendars.wpgateways.com
cpcontacts.wpgateways.com
ftp.wpgateways.com
mail.wpgateways.com
webdisk.wpgateways.com
webmail.wpgateways.com
whm.wpgateways.com
www.wpgateways.com

Showing 11 of 12. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • finley.ns.cloudflare.com
  • harlee.ns.cloudflare.com

MX records

  • _dc-mx.7a870b97a507.wpgateways.com

SPF policy

  • ip: 70.32.23.55/32
  • include: spf.a2hosting.com
  • include: helpscoutemail.com
  • a: wpgateways.com
  • mx: wpgateways.com
  • include: relay.mailchannels.net
  • ip: 104.219.251.253
  • ip: 174.136.12.123
  • ip: 68.66.216.4

Threat-feed evidence

History

Related pages

Pivot from wpgateways.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "wpgateways.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.