Skip to content

Hostname

getwebdefender.com

Last fetched

getwebdefender.com resolves to 104.21.20.127, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. getwebdefender.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 · getwebdefender.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/getwebdefender.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of getwebdefender.com owner
Contact emails
18443965-5b0b-4aa5-8c76-91f10dd8b3fe@identity-protect.org, 720ec978-484a-4db4-aee3-3880f793a97a@identity-protect.org, 84485472-e9f6-4d7b-9d0a-d388462dcf1a@identity-protect.org, c99eed8e-6632-42bd-becc-593d23c3ea22@identity-protect.org, d8685787-07d6-4c18-90e8-5e06b8cdb81e@identity-protect.org, f2959a8d-510f-4bae-a624-59024d576d9f@identity-protect.org, owner-1068669@getwebdefender.com.whoisprivacyservice.org

Subdomains

Subdomain
app.getwebdefender.com
support.getwebdefender.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • elinore.ns.cloudflare.com
  • gabe.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • getwebdefender-com.mail.protection.outlook.com

SPF policy

  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

Pivot from getwebdefender.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: "getwebdefender.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.