Skip to content

Hostname

getcopper.com

Last fetched

getcopper.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. getcopper.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 · getcopper.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/getcopper.com

Resolution chain

No IPv4 resolution is recorded for getcopper.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of getcopper.com owner
Contact emails
bnhmklrd@whoisprivacyprotect.com, cjgylvwgmk@whoisprivacyprotect.com, getcopper.com@domainsbyproxy.com, 1521dfe4-d448-46db-83c2-073a093ea52a@identity-protect.org, 30e53f36-3699-4f08-a666-1b631eb81f8e@identity-protect.org, 3ef05499-22e3-4d5c-ac6a-fbc5ce686987@identity-protect.org, 4d0825d6-4992-4586-9039-2cf6704d7f47@identity-protect.org, 8aaf464a-d12a-4765-ab59-de05cf827c98@identity-protect.org, a8178c47-61b3-40e0-9a2c-5515a70100b1@identity-protect.org, e1831a5e-2fc6-4597-8aa8-76e9058ae61b@identity-protect.org, owner-7840628@getcopper.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • ns-389.awsdns-48.com
  • ns-977.awsdns-58.net
  • ns-1234.awsdns-26.org
  • ns-1537.awsdns-00.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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