Skip to content

Hostname

quicken.sg

Last fetched

quicken.sg resolves to 4 IPv4 addresses operated by AS20940 in JP.

Nutrition Label

WHISPER CANON · quicken.sgRouting diversity2.4/10Peering density8.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.2/10canon.whisper.security/host/quicken.sg

Resolution chain

quicken.sg resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
23.220.70.4623.220.70.0/24AS20940—JP
23.220.70.823.220.70.0/24AS20940—JP
23.54.126.13123.54.126.0/24AS20940—MX
23.54.126.13923.54.126.0/24AS20940—MX

WHOIS identity

No WHOIS records are currently associated with quicken.sg in WhisperGraph.

Threat posture

History

Mail and authentication

MX records

SPF policy

7 SPF mechanisms authorising senders for quicken.sg.

MechanismTarget
SPF_IP12.149.175.17/29
SPF_IP208.29.163.248
SPF_IP208.74.45.50
SPF_IP64.18.0.0/20
SPF_IP65.79.182.20
SPF_IP67.135.240.36
SPF_MXintuit.com

Related pages

Pivot deeper into the graph from quicken.sg.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "quicken.sg"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.