Skip to content

Hostname

picovr.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:420
Registrant organisation
domain admin
Contact emails
developer@picovr.com, contact@privacyprotect.org

Subdomains

Subdomain
appstore.picovr.com
astatic-pui.picovr.com
avatar-global.picovr.com
bbs.picovr.com
mall.picovr.com
mon-global.picovr.com
passport.picovr.com
platform-sg.picovr.com
pui.picovr.com
qualcomm.picovr.com
sdk.picovr.com
sepsdiner.picovr.com

Showing 12 of 32. 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

Sample outbound links

Mail and authentication

Nameservers

  • vip3.alidns.com
  • vip4.alidns.com
  • ns-332.awsdns-41.com
  • ns-560.awsdns-06.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-1475.awsdns-56.org
  • ns-1769.awsdns-29.co.uk

MX records

  • mxbiz1.qq.com
  • mxbiz2.qq.com

SPF policy

  • include: spf.mail.qq.com

Threat-feed evidence

History

Related pages

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