[{"data":1,"prerenderedAt":638},["ShallowReactive",2],{"page-\u002Fguides\u002Fqr-code-domain-security":3,"related-\u002Fguides\u002Fqr-code-domain-security":616},{"id":4,"title":5,"author":6,"body":7,"category":601,"description":602,"extension":603,"heading":604,"heroImage":601,"heroImageAlt":605,"howTo":601,"layout":606,"meta":607,"navigation":608,"ogImage":609,"path":610,"publishedAt":611,"sections":601,"seo":612,"sourcePath":613,"stem":614,"updatedAt":611,"videoPosition":601,"videos":601,"__hash__":615},"pages\u002Fguides\u002Fqr-code-domain-security.md","QR code domain security: keep printed links alive","Mia",{"type":8,"value":9,"toc":579},"minimark",[10,17,30,33,47,52,55,133,136,140,150,163,167,176,185,188,203,207,210,232,235,239,246,261,264,268,271,280,287,291,306,309,317,321,330,338,342,498,506,510,539,543,548,551,555,558,562,565,569,572,576],[11,12,13],"p",{},[14,15,16],"strong",{},"TL;DR",[18,19,20,24,27],"ul",{},[21,22,23],"li",{},"QR code domain security is about the part of a printed code you cannot see: the domain registration, DNS records, TLS certificate and any redirect service behind the URL. The ink lasts for years; each of those layers can lapse, be taken over or be switched off.",[21,25,26],{},"The main failure modes are an expired domain that someone else registers, a hijacked registrar account, a forgotten DNS record that lets an outsider claim your subdomain, and a third-party link or \"dynamic QR\" service that closes or deactivates codes.",[21,28,29],{},"The fix is mostly governance: print codes on a domain or subdomain you own, lock and auto-renew it for several years, protect the registrar and DNS accounts with multi-factor authentication, monitor every printed URL pattern, and name an owner with a written exit plan.",[11,31,32],{},"A QR code on a carton does not stop working when the product leaves the shelf. It sits in kitchen cupboards, garages, second-hand shops and recycling sorting lines for years. Every time someone scans it, their phone asks a domain where to go. If that domain has expired, changed hands or been pointed somewhere else, the code on the pack is now somebody else's link, printed in your artwork. That is why QR code domain security matters as much as print quality.",[11,34,35,36,41,42,46],{},"This guide is about that infrastructure risk on the brand side. It is not a troubleshooting guide for a code that fails today (that is our ",[37,38,40],"a",{"href":39},"\u002Fguides\u002Fgs1-digital-link-not-resolving\u002F","GS1 Digital Link not resolving"," guide), and it is not about stickers placed over codes to trick shoppers (see ",[37,43,45],{"href":44},"\u002Fguides\u002Fwhat-is-quishing\u002F","what is quishing","). It is about keeping the web address in your printed codes under your control for as long as the products exist.",[48,49,51],"h2",{"id":50},"what-does-a-printed-qr-code-actually-depend-on","What does a printed QR code actually depend on?",[11,53,54],{},"The code itself is just a URL. Everything that makes it work lives elsewhere, and each layer has its own owner, renewal date and way to fail.",[56,57,58,74],"table",{},[59,60,61],"thead",{},[62,63,64,68,71],"tr",{},[65,66,67],"th",{},"Layer",[65,69,70],{},"What it does",[65,72,73],{},"How it fails",[75,76,77,89,100,111,122],"tbody",{},[62,78,79,83,86],{},[80,81,82],"td",{},"Domain registration",[80,84,85],{},"Gives you the right to use the name",[80,87,88],{},"Expiry, non-payment, account takeover, unauthorised transfer",[62,90,91,94,97],{},[80,92,93],{},"DNS records",[80,95,96],{},"Point the name (or a subdomain) at a server",[80,98,99],{},"Wrong or forgotten records, a compromised DNS account",[62,101,102,105,108],{},[80,103,104],{},"TLS certificate",[80,106,107],{},"Lets the phone open the page over HTTPS",[80,109,110],{},"Expiry, failed renewal, a blocked issuer",[62,112,113,116,119],{},[80,114,115],{},"Resolver or redirect service",[80,117,118],{},"Turns the code's URL into the right page",[80,120,121],{},"The service closes, the subscription lapses, the entry is deleted",[62,123,124,127,130],{},[80,125,126],{},"Destination page",[80,128,129],{},"Shows the product information",[80,131,132],{},"Deleted page, expired campaign, page behind a login",[11,134,135],{},"You can change a website's address next week. You cannot change the address printed on a million cartons already in people's homes.",[48,137,139],{"id":138},"how-long-does-a-printed-code-need-to-keep-working","How long does a printed code need to keep working?",[11,141,142,143,149],{},"At least as long as people keep the product, and for some products the law now says so. Under the Ecodesign for Sustainable Products Regulation, ",[37,144,148],{"href":145,"rel":146},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2024\u002F1781\u002Foj\u002Feng",[147],"nofollow","Regulation (EU) 2024\u002F1781",", Article 9(2)(i) says each delegated act will set the period during which the Digital Product Passport is to remain available, \"which shall correspond to at least the expected lifetime of a specific product\". Article 11(e) adds that the passport must remain available for that period \"including after an insolvency, a liquidation or a cessation of activity in the Union\" of the operator that created it. Article 10(1)(a) requires the passport to be connected through a data carrier to a persistent unique product identifier, and Article 10(4) requires a back-up copy with a passport service provider.",[11,151,152,153,157,158,162],{},"A back-up copy protects the data, but the code on the product still points at one specific address. Our ",[37,154,156],{"href":155},"\u002Fguides\u002Feu-regulation-2024-1781-espr\u002F","ESPR guide"," covers the regulation itself, and ",[37,159,161],{"href":160},"\u002Fguides\u002Fwho-is-responsible-for-the-digital-product-passport\u002F","who is responsible for the Digital Product Passport"," covers why the obligation stays with the economic operator even when a provider hosts the passport.",[48,164,166],{"id":165},"what-happens-when-a-domain-expires","What happens when a domain expires?",[11,168,169,170,175],{},"For generic top-level domains such as .com, ICANN's ",[37,171,174],{"href":172,"rel":173},"https:\u002F\u002Fwww.icann.org\u002Fresources\u002Fpages\u002Ferrp-2013-02-28-en",[147],"Expired Registration Recovery Policy"," gives you a short safety net. Registrars must send at least two reminders before expiry, at roughly one month and one week. After expiry the registrar has to interrupt DNS resolution for a period, so your codes stop working while you can still renew. If the registrar deletes the name, the registry must offer a 30-day redemption grace period during which it can be restored.",[11,177,178,179,184],{},"Then the net ends. According to ICANN's ",[37,180,183],{"href":181,"rel":182},"https:\u002F\u002Fwww.icann.org\u002Fresources\u002Fpages\u002Fdomain-name-renewal-expiration-faqs-2018-12-07-en",[147],"renewal and expiration FAQ",", a name that is not restored enters PendingDelete for 5 days, and \"After this period, the domain name will be released and made available for registration on a first-come-first-served basis.\" Specialist services register valuable names the instant they are released, a practice usually called drop-catching. A domain printed on packaging keeps receiving scans, exactly the traffic that makes a name attractive.",[11,186,187],{},"Country-code domains (.es, .de, .co.uk and so on) follow their own registry rules, so check the timeline for each one you use.",[11,189,190,191,196,197,202],{},"The usual causes are mundane: reminders going to someone who has left, an expired card, or a domain an agency registered for one campaign. The UK National Cyber Security Centre's guidance on ",[37,192,195],{"href":193,"rel":194},"https:\u002F\u002Fwww.ncsc.gov.uk\u002Fguidance\u002Fmanaging-public-domain-names",[147],"managing public domain names"," recommends auto-renewal paid through an organisational payment method rather than a personal card. ICANN's ",[37,198,201],{"href":199,"rel":200},"https:\u002F\u002Fwww.icann.org\u002Fnews\u002Fblog\u002Fdo-you-have-a-domain-name-here-s-what-you-need-to-know-part-4",[147],"advice to registrants"," adds a detail that is easy to miss: use a contact email that does not depend on the domain itself, or the reminders stop arriving at the same moment the domain stops working.",[48,204,206],{"id":205},"can-someone-take-over-the-domain-without-it-expiring","Can someone take over the domain without it expiring?",[11,208,209],{},"Yes. Whoever controls your registrar account controls where your codes lead. An attacker in that account can change the nameservers or transfer the domain away.",[11,211,212,213,218,219,223,224,227,228,231],{},"Registrar and registry locks reduce that risk. ICANN's ",[37,214,217],{"href":215,"rel":216},"https:\u002F\u002Fwww.icann.org\u002Fresources\u002Fpages\u002Fepp-status-codes-2014-06-16-en",[147],"EPP status codes"," explain that ",[220,221,222],"code",{},"clientTransferProhibited",", ",[220,225,226],{},"clientUpdateProhibited"," and ",[220,229,230],{},"clientDeleteProhibited"," tell the registry to reject transfers, updates and deletions, which helps prevent changes \"resulting from hijacking and\u002For fraud\". Some registries also offer a Registry Lock service, setting server-side codes that take longer to remove because your registrar has to work with the registry. ICANN notes that a transfer lock alone is \"not a fail-safe\" protection, so it belongs alongside account security, not instead of it.",[11,233,234],{},"The NCSC calls two-step verification at the registrar \"the most important recommendation\". Apply the same rule to the DNS host if it is a different company, and to any service that can change where your codes redirect.",[48,236,238],{"id":237},"what-is-a-dangling-dns-record-and-why-does-it-matter-for-qr-codes","What is a dangling DNS record, and why does it matter for QR codes?",[11,240,241,242,245],{},"Codes often run on a subdomain, such as ",[220,243,244],{},"qr.yourbrand.com",", pointed at a provider with a CNAME record. That is a sound setup. The risk starts when the service behind the record goes away and the record stays.",[11,247,248,249,254,255,260],{},"MDN describes the problem in its page on ",[37,250,253],{"href":251,"rel":252},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FSecurity\u002FAttacks\u002FSubdomain_takeover",[147],"subdomain takeovers",": a takeover typically happens \"when the subdomain has a canonical name (CNAME) in the Domain Name System (DNS), but no host is providing content for it.\" If the provider lets anyone claim that hostname, an outsider can set up their own content under your subdomain. Microsoft's guidance on ",[37,256,259],{"href":257,"rel":258},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fsecurity\u002Ffundamentals\u002Fsubdomain-takeover",[147],"dangling DNS entries"," lists the consequences, including phishing on an authentic-looking address, and warns that an attacker controlling the subdomain can obtain a valid certificate for it, so the padlock in the browser offers no protection.",[11,262,263],{},"For packaging, the timing makes this worse: the campaign microsite is switched off, and the codes on the cartons keep working for whoever claims the name. MDN's rule of thumb is simple: when provisioning, claim the host first and create the DNS record last; when deprovisioning, remove the DNS record first.",[48,265,267],{"id":266},"what-if-the-link-service-behind-the-code-shuts-down","What if the link service behind the code shuts down?",[11,269,270],{},"Many codes are not on the brand's domain at all. They point to a short link or a \"dynamic QR\" address on a vendor's domain, which then redirects to the brand's page. The printed code then depends on the vendor's business, terms and billing. Some services deactivate or redirect codes when a subscription ends; read the terms for what happens to existing codes if you stop paying or the service closes.",[11,272,273,274,279],{},"Large providers close services too. Google stopped taking new links for its URL shortener after 2018 and announced that goo.gl links would stop returning a response after 25 August 2025. In an ",[37,275,278],{"href":276,"rel":277},"https:\u002F\u002Fdevelopers.googleblog.com\u002Fgoogle-url-shortener-links-will-no-longer-be-available\u002F",[147],"update on its developer blog"," dated 1 August 2025, it narrowed the plan to links that had shown no activity in late 2024, while recommending that users move to another shortener. Links in documents can be edited. Links printed on products cannot.",[11,281,282,283,286],{},"The structural answer is to print your own domain. If the code carries ",[220,284,285],{},"yourbrand.com"," or a subdomain of it, you can move the service behind it to another provider by changing a DNS record, without reprinting. If it carries a vendor's domain, you cannot.",[48,288,290],{"id":289},"do-certificates-and-redirect-chains-matter","Do certificates and redirect chains matter?",[11,292,293,294,299,300,305],{},"Certificates expire, on a tightening timetable. Under the CA\u002FBrowser Forum ",[37,295,298],{"href":296,"rel":297},"https:\u002F\u002Fcabforum.org\u002Fworking-groups\u002Fserver\u002Fbaseline-requirements\u002Frequirements\u002F",[147],"Baseline Requirements",", following ",[37,301,304],{"href":302,"rel":303},"https:\u002F\u002Fcabforum.org\u002F2025\u002F04\u002F11\u002Fballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods\u002F",[147],"Ballot SC-081",", the maximum validity of a public TLS certificate is 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. Whoever serves your code's domain needs automated renewal and an alert when it fails.",[11,307,308],{},"Redirect chains add dependencies. A code that passes through a short link, a tracking domain and a campaign tool has several owners and certificates, each able to break or divert the scan. Keep the chain short: your domain and resolver, then the page.",[11,310,311,312,316],{},"A sticker placed over a genuine code is a different, physical attack on shoppers, covered in ",[37,313,315],{"href":314},"\u002Fguides\u002Fare-qr-codes-on-products-safe\u002F","are QR codes on products safe",".",[48,318,320],{"id":319},"why-gs1-digital-link-on-your-own-domain-helps","Why GS1 Digital Link on your own domain helps",[11,322,323,324,329],{},"GS1 designed its standard with this in mind. The ",[37,325,328],{"href":326,"rel":327},"https:\u002F\u002Fref.gs1.org\u002Fstandards\u002Fdigital-link\u002Furi-syntax\u002F",[147],"GS1 Digital Link URI Syntax"," states that a GS1 Digital Link URI \"can be constructed in any domain name\", a flexibility meant to ensure \"brands can remain in control of the domains they use\". The product identity (the GTIN, and batch or serial number if present) sits in the path, so it means the same thing whichever domain carries it.",[11,331,332,333,337],{},"So the domain in the code can be yours, and the governance above is in your hands. A 2D-ready checkout also reads the GTIN without going online, as our guide on whether ",[37,334,336],{"href":335},"\u002Fguides\u002Fdo-2d-barcodes-work-offline\u002F","2D barcodes work offline"," explains, so a web outage does not stop the sale. It does stop the shopper, repairer or recycler who scans for information.",[48,339,341],{"id":340},"checklist-qr-code-domain-security-for-brands","Checklist: QR code domain security for brands",[56,343,344,357],{},[59,345,346],{},[62,347,348,351,354],{},[65,349,350],{},"Control",[65,352,353],{},"What to do",[65,355,356],{},"Why",[75,358,359,370,381,392,403,414,431,448,465,476,487],{},[62,360,361,364,367],{},[80,362,363],{},"Own the domain",[80,365,366],{},"Print codes on a domain or subdomain your organisation owns, registered to the company, not to an agency or an employee",[80,368,369],{},"You can move the service behind it without reprinting",[62,371,372,375,378],{},[80,373,374],{},"Use GS1 Digital Link",[80,376,377],{},"Encode the GTIN in a GS1 Digital Link URI on that domain",[80,379,380],{},"The identity stays readable and standard whichever provider you use",[62,382,383,386,389],{},[80,384,385],{},"Renew for years",[80,387,388],{},"Auto-renew on an organisational payment method, registered several years ahead",[80,390,391],{},"Expiry is the commonest and most avoidable failure",[62,393,394,397,400],{},[80,395,396],{},"Lock it",[80,398,399],{},"Registrar locks on transfer, update and delete; registry lock for the main domain where offered",[80,401,402],{},"Blocks unauthorised transfers and changes",[62,404,405,408,411],{},[80,406,407],{},"Protect the accounts",[80,409,410],{},"Multi-factor authentication on registrar, DNS and resolver accounts; more than one named administrator; contact email off the domain",[80,412,413],{},"Account takeover bypasses every other control",[62,415,416,419,428],{},[80,417,418],{},"Sign the zone",[80,420,421,422,427],{},"Consider DNSSEC, which ",[37,423,426],{"href":424,"rel":425},"https:\u002F\u002Fwww.icann.org\u002Fresources\u002Fpages\u002Fdnssec-what-is-it-why-important-2019-03-05-en",[147],"ICANN explains"," lets resolvers detect forged or altered DNS answers",[80,429,430],{},"Integrity of where the code points",[62,432,433,436,445],{},[80,434,435],{},"Restrict certificate issuers",[80,437,438,439,444],{},"Publish CAA records, which under ",[37,440,443],{"href":441,"rel":442},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc8659.html",[147],"RFC 8659"," name the authorities allowed to issue certificates for your domain; agree the entries with any provider serving a subdomain",[80,446,447],{},"Makes mis-issuance harder",[62,449,450,453,462],{},[80,451,452],{},"Force HTTPS",[80,454,455,456,461],{},"Send an ",[37,457,460],{"href":458,"rel":459},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FReference\u002FHeaders\u002FStrict-Transport-Security",[147],"HSTS"," header on the code domain",[80,463,464],{},"Browsers upgrade to HTTPS and do not let users click through certificate errors",[62,466,467,470,473],{},[80,468,469],{},"Monitor",[80,471,472],{},"Check every printed URL pattern on a schedule, plus domain expiry, certificate expiry and changes to key DNS records",[80,474,475],{},"You hear about a problem before your customers do",[62,477,478,481,484],{},[80,479,480],{},"Clean up",[80,482,483],{},"Remove DNS records when a service is retired, DNS first",[80,485,486],{},"Prevents subdomain takeover",[62,488,489,492,495],{},[80,490,491],{},"Write it down",[80,493,494],{},"A register of printed domains and URL patterns, an owner for each, and an exit plan for every provider",[80,496,497],{},"Products outlast teams, agencies and contracts",[11,499,500,501,505],{},"Monitoring is the ",[37,502,504],{"href":503},"\u002Fguides\u002Fgs1-digital-link-testing\u002F","pre-print testing"," idea, repeated for the life of the product.",[48,507,509],{"id":508},"how-does-the-digital-link-platform-help","How does the Digital Link platform help?",[11,511,512,513,517,518,522,523,525,526,529,530,534,535,316],{},"Digital Link runs a GS1 conformant ",[37,514,516],{"href":515},"\u002Fproduct\u002Fdigital-link-resolver\u002F","resolver"," for GS1 Digital Link codes. With a ",[37,519,521],{"href":520},"\u002Fproduct\u002Fcustom-domain\u002F","custom domain",", codes can carry your own subdomain, such as ",[220,524,244],{},", instead of our generic domain: you add a CNAME record pointing to ",[220,527,528],{},"whitelabel.digitallink.ai"," at your DNS provider, then our support team completes the setup, including the certificate. The ",[37,531,533],{"href":532},"\u002Fhelp-center\u002Fhow-to-use-your-subdomain-for-digital-links\u002F","help centre article"," has the steps. Because the subdomain stays in your DNS, the domain registration, its renewal and the record itself remain under your control. Every link is dynamic, so destinations can be changed without reprinting. If you ever retire a subdomain, remove its CNAME record as part of the switch. To review how your printed codes are set up, write to ",[37,536,538],{"href":537},"mailto:support@digital-link.com","support@digital-link.com",[48,540,542],{"id":541},"frequently-asked-questions","Frequently asked questions",[544,545,547],"h3",{"id":546},"what-happens-to-my-qr-codes-if-my-domain-expires","What happens to my QR codes if my domain expires?",[11,549,550],{},"They stop working once the registrar interrupts DNS, and you have a limited window to renew. For generic top-level domains, a deleted name has a 30-day redemption period and then 5 days pending deletion, after which anyone can register it. From then on, every scan of your printed codes goes wherever the new owner decides.",[544,552,554],{"id":553},"is-a-subdomain-safe-to-use-for-qr-codes","Is a subdomain safe to use for QR codes?",[11,556,557],{},"Yes, if the parent domain is well governed and the record is managed with care. A subdomain on your own domain is portable: you can point it at another provider without reprinting. The risk is a CNAME left pointing at a service you no longer use, which can allow a subdomain takeover.",[544,559,561],{"id":560},"do-dynamic-qr-codes-stop-working-when-the-subscription-ends","Do dynamic QR codes stop working when the subscription ends?",[11,563,564],{},"It depends on the provider and its terms. If the code carries the provider's domain, its behaviour after cancellation is the provider's decision. If it carries your own domain, you can redirect it to a new service yourself.",[544,566,568],{"id":567},"does-dnssec-protect-my-qr-codes-from-hijacking","Does DNSSEC protect my QR codes from hijacking?",[11,570,571],{},"Partly. DNSSEC lets resolvers detect forged or altered DNS answers. It does not stop someone who has logged into your registrar or DNS account from changing the records legitimately, so multi-factor authentication and registrar locks matter as much.",[544,573,575],{"id":574},"how-long-should-a-qr-code-on-packaging-keep-working","How long should a QR code on packaging keep working?",[11,577,578],{},"At least as long as the product is in use. For products covered by ESPR delegated acts, the Digital Product Passport must remain available for at least the expected lifetime of the product, including after insolvency or cessation of activity, so plan the domain for that horizon.",{"title":580,"searchDepth":581,"depth":581,"links":582},"",3,[583,585,586,587,588,589,590,591,592,593,594],{"id":50,"depth":584,"text":51},2,{"id":138,"depth":584,"text":139},{"id":165,"depth":584,"text":166},{"id":205,"depth":584,"text":206},{"id":237,"depth":584,"text":238},{"id":266,"depth":584,"text":267},{"id":289,"depth":584,"text":290},{"id":319,"depth":584,"text":320},{"id":340,"depth":584,"text":341},{"id":508,"depth":584,"text":509},{"id":541,"depth":584,"text":542,"children":595},[596,597,598,599,600],{"id":546,"depth":581,"text":547},{"id":553,"depth":581,"text":554},{"id":560,"depth":581,"text":561},{"id":567,"depth":581,"text":568},{"id":574,"depth":581,"text":575},null,"QR code domain security for brands: how expired domains, hijacked registrar accounts, dangling DNS and closed link services break printed codes, and what to do.","md","Your QR code will outlive your domain: QR code domain security for brands","An operations manager at a desk holding an old product carton with a QR code, comparing it with a printed list of domains and renewal dates","article",{},true,"\u002Fimages\u002F2026\u002F11\u002Fqr-code-domain-security-hero.webp","\u002Fguides\u002Fqr-code-domain-security","2026-11-17T10:00:00+01:00",{"title":5,"description":602},"\u002Fguides\u002Fqr-code-domain-security\u002F","guides\u002Fqr-code-domain-security","7-_tkHO-oSLGUyhp_YGs2gzfi03Re9hpPh4T02BX73Y",[617,624,631],{"path":618,"sourcePath":619,"title":620,"heading":621,"ogImage":622,"publishedAt":623},"\u002Fguides\u002Fdpp-registry-api","\u002Fguides\u002Fdpp-registry-api\u002F","DPP Registry API: what integration actually involves","DPP Registry API: how to register battery passports with the EU, step by step","\u002Fimages\u002F2026\u002F11\u002Fdpp-registry-api-hero.webp","2026-11-10T13:00:00+01:00",{"path":625,"sourcePath":626,"title":627,"heading":628,"ogImage":629,"publishedAt":630},"\u002Fguides\u002Fagentic-commerce","\u002Fguides\u002Fagentic-commerce\u002F","Agentic commerce: how AI agents buy and what products need","Agentic commerce: how AI agents buy, and what your product needs","\u002Fimages\u002F2026\u002F11\u002Fagentic-commerce-hero.webp","2026-11-03T12:13:00+01:00",{"path":632,"sourcePath":633,"title":634,"heading":635,"ogImage":636,"publishedAt":637},"\u002Fguides\u002Fmachine-readable-digital-product-passport","\u002Fguides\u002Fmachine-readable-digital-product-passport\u002F","The machine-readable Digital Product Passport, explained","The machine-readable Digital Product Passport: what the ESPR requires, and why AI agents will read it","\u002Fimages\u002F2026\u002F11\u002Fmachine-readable-digital-product-passport-hero.webp","2026-11-02T11:00:00+01:00",1794937163801]