Skip to content

Hostname

quickquack.com

Last fetched

quickquack.com resolves to 35.160.44.228, announced in 35.160.0.0/13 by AMAZON-02 - Amazon.com, Inc. in US. quickquack.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 · quickquack.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/quickquack.com

Resolution chain

IPv6 resolution

No AAAA record for quickquack.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of quickquack.com owner
Contact emails
info@dontdrivedirty.com, 137fe9de-cf85-4d47-9a30-01479cd8de41@identity-protect.org, 18e99bc7-5b35-47d7-a440-eabb080a26e4@identity-protect.org, 1ad143bc-90fb-43d8-87cf-d38800e7ad41@identity-protect.org, b8527099-c434-4e4d-918b-39ee2eecd920@identity-protect.org, c47dd856-6cf4-4a10-ac13-baf532bafdbe@identity-protect.org, e95e08af-849c-43ba-bd3b-c4e3f124c35b@identity-protect.org, owner-2627716@quickquack.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-247.awsdns-30.com
  • ns-717.awsdns-25.net
  • 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
  • ns-1391.awsdns-45.org
  • ns-1802.awsdns-33.co.uk

MX records

  • quickquack-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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