Skip to content

Hostname

kingopinion.com

Last fetched

kingopinion.com resolves to 108.131.196.152, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. kingopinion.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 · kingopinion.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/kingopinion.com

Resolution chain

IPv6 resolution

IPv6 resolution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of kingopinion.com owner
Contact emails
ltl5irgj6xvfoq8pn7ce@u.o-w-o.info, 2e23f81f-b24a-44be-91e8-85e055cf87e2@identity-protect.org, 69cebf94-a95f-413b-b4aa-5e5e54360539@identity-protect.org, 709dfe5e-c8e6-4dcf-94af-b0819321679a@identity-protect.org, 73a1d502-c83e-4954-8ada-9122dbebfecf@identity-protect.org, b0340a41-070f-4fb5-ba15-68deac0b7694@identity-protect.org

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • ns-433.awsdns-54.com
  • ns-882.awsdns-46.net
  • ns-1149.awsdns-15.org
  • ns-1911.awsdns-46.co.uk

MX records

  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • smtp.google.com

Threat-feed evidence

History

Related pages

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