Hostname
quickbooksconnect.com
Last fetched
quickbooksconnect.com resolves to 104.81.5.252, announced in 104.81.0.0/20 by AKAMAI-AS - Akamai Technologies, Inc. in DE. quickbooksconnect.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
- 104.81.5.252
104.81.0.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
- 23.201.173.163
23.201.160.0/19 · AKAMAI-AS - Akamai Technologies, Inc. · Secaucus, US
- 23.205.238.171
23.205.232.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Buenos Aires, AR
- 23.210.119.18
23.210.112.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.215.22.194
23.215.16.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.56.207.190
23.56.200.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for quickbooksconnect.com is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- domain administrator
- Contact emails
- nadmin@intuit.com
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
- a1-182.akam.net
- a11-64.akam.net
- a18-64.akam.net
- a24-67.akam.net
- a6-66.akam.net
- a7-66.akam.net
- dns1.p01.nsone.net
- dns2.p01.nsone.net
- dns3.p01.nsone.net
- dns4.p01.nsone.net
MX records
- mailin.intuit.com
- mta01-lv.intuit.com
SPF policy
- ip: 64.18.0.0/20
- ip: 206.108.40.0/21
- ip: 66.179.50.160/27
- ip: 12.149.175.17/29
- include: _spf.centercode.com
- mx: intuit.com
- ip: 208.29.163.248
- ip: 208.74.45.50
- ip: 65.79.182.20
- ip: 67.135.240.36
Threat-feed evidence
History
Related pages
Pivot from quickbooksconnect.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: "quickbooksconnect.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.