Hostname
picardyproject.com
Last fetched
picardyproject.com resolves to 208.80.5.214, announced in 208.80.4.0/22 by TIGERTECH - Tiger Technologies LLC in US. picardyproject.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 208.80.5.214
208.80.4.0/22 · TIGERTECH - Tiger Technologies LLC · Berkeley, US
IPv6 resolution
No AAAA record for picardyproject.com is recorded in WhisperGraph.
Attribution
tiger
ORIGIN_AS
WHOIS identity
- Registrar
- iana:841
- Registrant organisation
- domain administrator
- Contact emails
- picardyproject.com-owner-201609-0c8f62@whois.tigertech.net, picardyproject.com-owner-201711-74d6b5@whois.tigertech.net, picardyproject.com-owner-202309-98eaca@whois.tigertech.net, picardyproject.com-owner-202311-a6fb94@whois.tigertech.net, picardyproject.com-owner-202401-b03974@whois.tigertech.net, picardyproject.com-owner-202402-5e001f@whois.tigertech.net, picardyproject.com-owner-202403-7f47cf@whois.tigertech.net, picardyproject.com-owner-202405-fbc967@whois.tigertech.net, picardyproject.com-owner-202407-be3661@whois.tigertech.net, picardyproject.com-owner-202409-388ce1@whois.tigertech.net, picardyproject.com-owner-202411-ba6af6@whois.tigertech.net, picardyproject.com-owner-202501-3f7930@whois.tigertech.net
Subdomains
Showing 2 of 2 subdomains (2 per page).
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
Mail and authentication
Nameservers
- ns2.tigertech.biz
- ns1.tigertech.net
- ns3.tigertech.org
MX records
- mx1.tigertech.net
- mx2.tigertech.net
- mx3.tigertech.net
SPF policy
- include: tigertech.net
Threat-feed evidence
History
Related pages
Pivot from picardyproject.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: "picardyproject.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.