Hostname
lectorlive.com
Last fetched
lectorlive.com resolves to 18.205.143.244, announced in 18.204.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. lectorlive.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
- 18.205.143.244
18.204.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.215.132.239
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.227.186.236
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.233.75.206
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.90.116.215
3.80.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.206.148.137
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.233.41.167
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.235.1.157
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.175.98.145
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 50.19.213.190
50.19.128.0/17 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.20.179.189
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.20.243.157
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.45.116.91
52.44.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.7.53.34
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.7.56.27
52.4.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.158.94.53
54.156.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.86.245.206
54.86.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.55.230.203
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.193.173.107
32.192.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.55.254.116
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for lectorlive.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:303
- Registrant organisation
- alex sandro da silva
- Contact emails
- alex@lectortec.com.br
Company
- Company
- Lector Live
Technology
Lector Live has been observed using 16 technologies somewhere in its estate. This is observed use, not an exposure finding.
- Google Fonts API · font scripts
- Font Awesome · font scripts
- Google Analytics · intelligence and analytics
- Nginx · web servers
- Google Tag Manager · tag management
- Amazon Web Services · cloud hosting
- gstatic.com · content delivery network
- PWA · miscellaneous
- cdnjs · content delivery network
- jsDelivr · content delivery network
- HTML5 Mobile Boilerplate · mobile application development platforms
- Amazon Route 53 · domain name services
- Google Sign-in · identity verification
- Mailgun · email
- Firebase · database
- AngularJS · javascript frameworks
Subdomains
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for lectorlive.com.
DKIM signing
No DKIM signing vendor is attributed to lectorlive.com in WhisperGraph.
Nameservers
- ns-89.awsdns-11.com
- ns-881.awsdns-46.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-1377.awsdns-44.org
- ns-1794.awsdns-32.co.uk
MX records
- mxa.mailgun.org
- mxb.mailgun.org
SPF policy
- include: spf.mandrillapp.com
- include: mailgun.org
Threat-feed evidence
History
Related pages
Pivot from lectorlive.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN) WHERE conflict.name IS NOT NULL
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.